projects / ostree.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: e5e0b95) | patch
reset: Don't enforce parent commits
authorColin Walters <walters@verbum.org>
Wed, 8 Apr 2015 00:54:37 +0000 (20:54 -0400)
committerColin Walters <walters@verbum.org>
Wed, 15 Apr 2015 11:12:20 +0000 (07:12 -0400)
commitab15eafe56fc4e237010a967a31740558a493ab8
tree7d4ff34ca0b127b8c7367b00ed63212cbf28ec39tree | snapshot
parente5e0b95e27bf8c2c72938aaea95eacebea14c40bcommit | diff
reset: Don't enforce parent commits

First, git doesn't do this, and whatever Linus thinks is right or
something.

Second specifically to OSTree, it's quite common to not have
intermediate commits.  If one wants to reset a ref in order to prune
data after a deployment, the parentage check will fail.

Closes: https://github.com/GNOME/ostree/pull/87
Makefile-tests.am diff | blob | history
src/ostree/ot-builtin-reset.c diff | blob | history
tests/test-reset-nonlinear.sh [new file with mode: 0755] blob
Unnamed repository; edit this file 'description' to name the repository.